Infrastructure aware adaptive resource allocation

ABSTRACT

Disclosed are systems, methods, and computer-readable storage media for infrastructure aware adaptive resource allocation. A resource manager can receive a request to allocate a first container instance in a network. The resource manager can determine a set of candidate computing nodes in the network that are capable of hosting the first container instance and request, from an infrastructure monitor that received infrastructure data from the network, health metrics for the set of candidate computing nodes. The resource manager can select, based on the health metrics for the set of candidate computing nodes, an optimal computing node to host the first container instance, and allocate the first container instance on the optimal computing node.

CROSS-REFERENCE TO RELATED APPLICATION

This application is a continuation of U.S. patent application Ser. No.15/250,867, filed on Aug. 29, 2016, the content of which is incorporatedby reference in its entirety.

TECHNICAL FIELD

This disclosure relates in general to the field of computer networksand, more particularly, pertains to infrastructure aware adaptiveresource allocation.

BACKGROUND

Container based architecture is quickly being adopted in the DataCenter/Cloud Industry. Rather than building a single large, monolithicapplication, container based micro-services split the application into aset of smaller interconnected services. Container management (e.g.,resource allocation, scheduling, container/VM placement, QoS, resourceutilization, scaling, etc.) is critical to containerization of datacenter applications. Current resource managers only look at theresources utilized by various applications and where resources areavailable to use when allocating containers. They are, however, agnosticto the underlying infrastructure and other shared resources, such as thenetwork, power and security. Accordingly, improvements are needed.

BRIEF DESCRIPTION OF THE DRAWINGS

In order to describe the manner in which the above-recited features andother advantages of the disclosure can be obtained, a more particulardescription of the principles briefly described above will be renderedby reference to specific embodiments thereof, which are illustrated inthe appended drawings. Understanding that these drawings depict onlyexemplary embodiments of the disclosure and are not therefore to beconsidered to be limiting its scope, the principles herein are describedand explained with additional specificity and detail through the use ofthe accompanying drawings in which:

FIG. 1 illustrates an example network device according to some aspectsof the subject technology;

FIGS. 2A and 2B illustrate an example system embodiments according tosome aspects of the subject technology;

FIG. 3 illustrates a schematic block diagram of an example architecturefor a network fabric;

FIG. 4 illustrates an example overlay network;

FIGS. 5A and 5B illustrate an example of infrastructure aware adaptiveresource allocation; and

FIG. 6 illustrates an example method of infrastructure aware adaptiveresource allocation.

DESCRIPTION OF EXAMPLE EMBODIMENTS

The detailed description set forth below is intended as a description ofvarious configurations of the subject technology and is not intended torepresent the only configurations in which the subject technology can bepracticed. The appended drawings are incorporated herein and constitutea part of the detailed description. The detailed description includesspecific details for the purpose of providing a more thoroughunderstanding of the subject technology. However, it will be clear andapparent that the subject technology is not limited to the specificdetails set forth herein and may be practiced without these details. Insome instances, structures and components are shown in block diagramform in order to avoid obscuring the concepts of the subject technology.

Overview:

Disclosed are systems, methods, and computer-readable storage media forinfrastructure aware adaptive resource allocation. A resource managercan receive a request to allocate a first container instance in anetwork. The resource manager can determine a set of candidate computingnodes in the network that are capable of hosting the first containerinstance and request, from an infrastructure monitor that receivesinfrastructure data from the network, health metrics for the set ofcandidate computing nodes. The resource manager can select, based on thehealth metrics for the set of candidate computing nodes, an optimalcomputing node to host the first container instance, and allocate thefirst container instance on the optimal computing node.

DETAILED DESCRIPTION

Disclosed are systems and methods for infrastructure aware adaptiveresource allocation. A brief introductory description of exemplarysystems and networks, as illustrated in FIGS. 1 through 4, is disclosedherein, followed by a discussion of infrastructure aware adaptiveresource allocation. The disclosure now turns to FIG. 1.

A computer network is a geographically distributed collection of nodesinterconnected by communication links and segments for transporting databetween endpoints, such as personal computers and workstations. Manytypes of networks are available, with the types ranging from local areanetworks (LANs) and wide area networks (WANs) to overlay andsoftware-defined networks, such as virtual extensible local areanetworks (VXLANs).

LANs typically connect nodes over dedicated private communications linkslocated in the same general physical location, such as a building orcampus. WANs, on the other hand, typically connect geographicallydispersed nodes over long-distance communications links, such as commoncarrier telephone lines, optical lightpaths, synchronous opticalnetworks (SONET), or synchronous digital hierarchy (SDH) links. LANs andWANs can include layer 2 (L2) and/or layer 3 (L3) networks and devices.

The Internet is an example of a WAN that connects disparate networksthroughout the world, providing global communication between nodes onvarious networks. The nodes typically communicate over the network byexchanging discrete frames or packets of data according to predefinedprotocols, such as the Transmission Control Protocol/Internet Protocol(TCP/IP). In this context, a protocol can refer to a set of rulesdefining how the nodes interact with each other. Computer networks maybe further interconnected by an intermediate network node, such as arouter, to extend the effective “size” of each network.

Overlay networks generally allow virtual networks to be created andlayered over a physical network infrastructure. Overlay networkprotocols, such as Virtual Extensible LAN (VXLAN), NetworkVirtualization using Generic Routing Encapsulation (NVGRE), NetworkVirtualization Overlays (NVO3), and Stateless Transport Tunneling (STT),provide a traffic encapsulation scheme which allows network traffic tobe carried across L2 and L3 networks over a logical tunnel. Such logicaltunnels can be originated and terminated through virtual tunnel endpoints (VTEPs).

Moreover, overlay networks can include virtual segments, such as VXLANsegments in a VXLAN overlay network, which can include virtual L2 and/orL3 overlay networks over which virtual machines (VMs) communicate. Thevirtual segments can be identified through a virtual network identifier(VNI), such as a VXLAN network identifier, which can specificallyidentify an associated virtual segment or domain.

Network virtualization allows hardware and software resources to becombined in a virtual network. For example, network virtualization canallow multiple numbers of VMs to be attached to the physical network viarespective virtual LANs (VLANs). The VMs can be grouped according totheir respective VLAN, and can communicate with other VMs as well asother devices on the internal or external network.

Network segments, such as physical or virtual segments; networks;devices; ports; physical or logical links; and/or traffic in general canbe grouped into a bridge or flood domain. A bridge domain or flooddomain can represent a broadcast domain, such as an L2 broadcast domain.A bridge domain or flood domain can include a single subnet, but canalso include multiple subnets. Moreover, a bridge domain can beassociated with a bridge domain interface on a network device, such as aswitch. A bridge domain interface can be a logical interface whichsupports traffic between an L2 bridged network and an L3 routed network.In addition, a bridge domain interface can support internet protocol(IP) termination, VPN termination, address resolution handling, MACaddressing, etc. Both bridge domains and bridge domain interfaces can beidentified by a same index or identifier.

Furthermore, endpoint groups (EPGs) can be used in a network for mappingapplications to the network. In particular, EPGs can use a grouping ofapplication endpoints in a network to apply connectivity and policy tothe group of applications. EPGs can act as a container for buckets orcollections of applications, or application components, and tiers forimplementing forwarding and policy logic. EPGs also allow separation ofnetwork policy, security, and forwarding from addressing by insteadusing logical application boundaries.

Cloud computing can also be provided in one or more networks to providecomputing services using shared resources. Cloud computing can generallyinclude Internet-based computing in which computing resources aredynamically provisioned and allocated to client or user computers orother devices on-demand, from a collection of resources available viathe network (e.g., “the cloud”). Cloud computing resources, for example,can include any type of resource, such as computing, storage, andnetwork devices, virtual machines (VMs), etc. For instance, resourcesmay include service devices (firewalls, deep packet inspectors, trafficmonitors, load balancers, etc.), compute/processing devices (servers,CPU's, memory, brute force processing capability), storage devices(e.g., network attached storages, storage area network devices), etc. Inaddition, such resources may be used to support virtual networks,virtual machines (VM), databases, applications (Apps), etc.

Cloud computing resources may include a “private cloud,” a “publiccloud,” and/or a “hybrid cloud.” A “hybrid cloud” can be a cloudinfrastructure composed of two or more clouds that inter-operate orfederate through technology. In essence, a hybrid cloud is aninteraction between private and public clouds where a private cloudjoins a public cloud and utilizes public cloud resources in a secure andscalable manner. Cloud computing resources can also be provisioned viavirtual networks in an overlay network, such as a VXLAN.

FIG. 1 illustrates an exemplary network device 110 suitable forimplementing the present technology. Network device 110 includes amaster central processing unit (CPU) 162, interfaces 168, and a bus 115(e.g., a PCI bus). When acting under the control of appropriate softwareor firmware, the CPU 162 is responsible for executing packet management,error detection, and/or routing functions, such as policy enforcement,for example. The CPU 162 preferably accomplishes all these functionsunder the control of software including an operating system and anyappropriate applications software. CPU 162 may include one or moreprocessors 163 such as a processor from the Motorola family ofmicroprocessors or the MIPS family of microprocessors. In an alternativeembodiment, processor 163 is specially designed hardware for controllingthe operations of router 110. In a specific embodiment, a memory 161(such as non-volatile RAM and/or ROM) also forms part of CPU 162.However, there are many different ways in which memory could be coupledto the system.

The interfaces 168 are typically provided as interface cards (sometimesreferred to as “line cards”). Generally, they control the sending andreceiving of data packets over the network and sometimes support otherperipherals used with the network device 110. Among the interfaces thatmay be provided are Ethernet interfaces, frame relay interfaces, cableinterfaces, DSL interfaces, token ring interfaces, and the like. Inaddition, various very high-speed interfaces may be provided such asfast token ring interfaces, wireless interfaces, Ethernet interfaces,Gigabit Ethernet interfaces, ATM interfaces, HSSI interfaces, POSinterfaces, FDDI interfaces and the like. Generally, these interfacesmay include ports appropriate for communication with the appropriatemedia. In some cases, they may also include an independent processorand, in some instances, volatile RAM. The independent processors maycontrol such communications intensive tasks as packet switching, mediacontrol, and management. By providing separate processors for thecommunications intensive tasks, these interfaces allow the mastermicroprocessor 162 to efficiently perform routing computations, networkdiagnostics, security functions, etc.

Although the system shown in FIG. 1 is one specific network device ofthe present technology, it is by no means the only network devicearchitecture on which the present technology can be implemented. Forexample, an architecture having a single processor that handlescommunications as well as routing computations, etc. is often used.Further, other types of interfaces and media could also be used with therouter.

Regardless of the network device's configuration, it may employ one ormore memories or memory modules (including memory 161) configured tostore program instructions for the general-purpose network operationsand mechanisms for roaming, route optimization and routing functionsdescribed herein. The program instructions may control the operation ofan operating system and/or one or more applications, for example. Thememory or memories may also be configured to store tables such asmobility binding, registration, and association tables, etc.

FIG. 2A, and FIG. 2B illustrate exemplary possible system embodiments.The more appropriate embodiment will be apparent to those of ordinaryskill in the art when practicing the present technology. Persons ofordinary skill in the art will also readily appreciate that other systemembodiments are possible.

FIG. 2A illustrates a conventional system bus computing systemarchitecture 200 wherein the components of the system are in electricalcommunication with each other using a bus 205. Exemplary system 200includes a processing unit (CPU or processor) 210 and a system bus 205that couples various system components including the system memory 215,such as read only memory (ROM) 220 and random access memory (RAM) 225,to the processor 210. The system 200 can include a cache of high-speedmemory connected directly with, in close proximity to, or integrated aspart of the processor 210. The system 200 can copy data from the memory215 and/or the storage device 230 to the cache 212 for quick access bythe processor 210. In this way, the cache can provide a performanceboost that avoids processor 210 delays while waiting for data. These andother modules can control or be configured to control the processor 210to perform various actions. Other system memory 215 may be available foruse as well. The memory 215 can include multiple different types ofmemory with different performance characteristics. The processor 210 caninclude any general purpose processor and a hardware module or softwaremodule, such as module 1 232, module 2 234, and module 3 236 stored instorage device 230, configured to control the processor 210 as well as aspecial-purpose processor where software instructions are incorporatedinto the actual processor design. The processor 210 may essentially be acompletely self-contained computing system, containing multiple cores orprocessors, a bus, memory controller, cache, etc. A multi-core processormay be symmetric or asymmetric.

To enable user interaction with the computing device 200, an inputdevice 245 can represent any number of input mechanisms, such as amicrophone for speech, a touch-sensitive screen for gesture or graphicalinput, keyboard, mouse, motion input, speech and so forth. An outputdevice 235 can also be one or more of a number of output mechanismsknown to those of skill in the art. In some instances, multimodalsystems can enable a user to provide multiple types of input tocommunicate with the computing device 200. The communications interface240 can generally govern and manage the user input and system output.There is no restriction on operating on any particular hardwarearrangement and therefore the basic features here may easily besubstituted for improved hardware or firmware arrangements as they aredeveloped.

Storage device 230 is a non-volatile memory and can be a hard disk orother types of computer readable media which can store data that areaccessible by a computer, such as magnetic cassettes, flash memorycards, solid state memory devices, digital versatile disks, cartridges,random access memories (RAMs) 225, read only memory (ROM) 220, andhybrids thereof.

The storage device 230 can include software modules 232, 234, 236 forcontrolling the processor 210. Other hardware or software modules arecontemplated. The storage device 230 can be connected to the system bus205. In one aspect, a hardware module that performs a particularfunction can include the software component stored in acomputer-readable medium in connection with the necessary hardwarecomponents, such as the processor 210, bus 205, display 235, and soforth, to carry out the function.

FIG. 2B illustrates a computer system 250 having a chipset architecturethat can be used in executing the described method and generating anddisplaying a graphical user interface (GUI). Computer system 250 is anexample of computer hardware, software, and firmware that can be used toimplement the disclosed technology. System 250 can include a processor255, representative of any number of physically and/or logicallydistinct resources capable of executing software, firmware, and hardwareconfigured to perform identified computations. Processor 255 cancommunicate with a chipset 260 that can control input to and output fromprocessor 255. In this example, chipset 260 outputs information tooutput 265, such as a display, and can read and write information tostorage device 270, which can include magnetic media, and solid statemedia, for example. Chipset 260 can also read data from and write datato RAM 275. A bridge 280 for interfacing with a variety of userinterface components 285 can be provided for interfacing with chipset260. Such user interface components 285 can include a keyboard, amicrophone, touch detection and processing circuitry, a pointing device,such as a mouse, and so on. In general, inputs to system 250 can comefrom any of a variety of sources, machine generated and/or humangenerated.

Chipset 260 can also interface with one or more communication interfaces290 that can have different physical interfaces. Such communicationinterfaces can include interfaces for wired and wireless local areanetworks, for broadband wireless networks, as well as personal areanetworks. Some applications of the methods for generating, displaying,and using the GUI disclosed herein can include receiving ordereddatasets over the physical interface or be generated by the machineitself by processor 255 analyzing data stored in storage 270 or 275.Further, the machine can receive inputs from a user via user interfacecomponents 285 and execute appropriate functions, such as browsingfunctions by interpreting these inputs using processor 255.

It can be appreciated that exemplary systems 200 and 250 can have morethan one processor 210 or be part of a group or cluster of computingdevices networked together to provide greater processing capability.

FIG. 3 illustrates a schematic block diagram of an example architecture300 for a network fabric 312. The network fabric 312 can include spineswitches 302 _(A), 302 _(B), . . . , 302 _(N) (collectively “302”)connected to leaf switches 304 _(A), 304 _(B), 304 _(C) . . . 304 _(N)(collectively “304”) in the network fabric 312.

Spine switches 302 can be L3 switches in the fabric 312. However, insome cases, the spine switches 302 can also, or otherwise, perform L2functionalities. Further, the spine switches 302 can support variouscapabilities, such as 40 or 10 Gbps Ethernet speeds. To this end, thespine switches 302 can include one or more 40 Gigabit Ethernet ports.Each port can also be split to support other speeds. For example, a 40Gigabit Ethernet port can be split into four 10 Gigabit Ethernet ports.

In some embodiments, one or more of the spine switches 302 can beconfigured to host a proxy function that performs a lookup of theendpoint address identifier to locator mapping in a mapping database onbehalf of leaf switches 304 that do not have such mapping. The proxyfunction can do this by parsing through the packet to the encapsulatedtenant packet to get to the destination locator address of the tenant.The spine switches 302 can then perform a lookup of their local mappingdatabase to determine the correct locator address of the packet andforward the packet to the locator address without changing certainfields in the header of the packet.

When a packet is received at a spine switch 302 _(i), the spine switch302 _(i) can first check if the destination locator address is a proxyaddress. If so, the spine switch 302 _(i) can perform the proxy functionas previously mentioned. If not, the spine switch 302 _(i) can look upthe locator in its forwarding table and forward the packet accordingly.

Spine switches 302 connect to leaf switches 304 in the fabric 312. Leafswitches 304 can include access ports (or non-fabric ports) and fabricports. Fabric ports can provide uplinks to the spine switches 302, whileaccess ports can provide connectivity for devices, hosts, endpoints,VMs, or external networks to the fabric 312.

Leaf switches 304 can reside at the edge of the fabric 312, and can thusrepresent the physical network edge. In some cases, the leaf switches304 can be top-of-rack (“ToR”) switches configured according to a ToRarchitecture. In other cases, the leaf switches 304 can be aggregationswitches in any particular topology, such as end-of-row (EoR) ormiddle-of-row (MoR) topologies. The leaf switches 304 can also representaggregation switches, for example.

The leaf switches 304 can be responsible for routing and/or bridging thetenant packets and applying network policies. In some cases, a leafswitch can perform one or more additional functions, such asimplementing a mapping cache, sending packets to the proxy function whenthere is a miss in the cache, encapsulate packets, enforce ingress oregress policies, etc.

Moreover, the leaf switches 304 can contain virtual switchingfunctionalities, such as a virtual tunnel endpoint (VTEP) function asexplained below in the discussion of VTEP 408 in FIG. 4. To this end,leaf switches 304 can connect the fabric 312 to an overlay network, suchas overlay network 400 illustrated in FIG. 4.

Network connectivity in the fabric 312 can flow through the leafswitches 304. Here, the leaf switches 304 can provide servers,resources, endpoints, external networks, or VMs access to the fabric312, and can connect the leaf switches 304 to each other. In some cases,the leaf switches 304 can connect EPGs to the fabric 312 and/or anyexternal networks. Each EPG can connect to the fabric 312 via one of theleaf switches 304, for example.

Endpoints 310A-E (collectively “310”) can connect to the fabric 312 vialeaf switches 304. For example, endpoints 310A and 310B can connectdirectly to leaf switch 304A, which can connect endpoints 310A and 310Bto the fabric 312 and/or any other one of the leaf switches 304.Similarly, endpoint 310E can connect directly to leaf switch 304C, whichcan connect endpoint 310E to the fabric 312 and/or any other of the leafswitches 304. On the other hand, endpoints 310C and 310D can connect toleaf switch 304B via L2 network 306. Similarly, the wide area network(WAN) can connect to the leaf switches 304C or 304D via L3 network 308.

Endpoints 310 can include any communication device, such as a computer,a server, a switch, a router, etc. In some cases, the endpoints 310 caninclude a server, hypervisor, or switch configured with a VTEPfunctionality which connects an overlay network, such as overlay network400 below, with the fabric 312. For example, in some cases, theendpoints 310 can represent one or more of the VTEPs 408A-D illustratedin FIG. 4. Here, the VTEPs 408A-D can connect to the fabric 312 via theleaf switches 304. The overlay network can host physical devices, suchas servers, applications, EPGs, virtual segments, virtual workloads,etc. In addition, the endpoints 310 can host virtual workload(s),clusters, and applications or services, which can connect with thefabric 312 or any other device or network, including an externalnetwork. For example, one or more endpoints 310 can host, or connect to,a cluster of load balancers or an EPG of various applications.

Although the fabric 312 is illustrated and described herein as anexample leaf-spine architecture, one of ordinary skill in the art willreadily recognize that the subject technology can be implemented basedon any network fabric, including any data center or cloud networkfabric. Indeed, other architectures, designs, infrastructures, andvariations are contemplated herein.

FIG. 4 illustrates an exemplary overlay network 400. Overlay network 400uses an overlay protocol, such as VXLAN, VGRE, VO3, or STT, toencapsulate traffic in L2 and/or L3 packets which can cross overlay L3boundaries in the network. As illustrated in FIG. 4, overlay network 400can include hosts 406A-D interconnected via network 402.

Network 402 can include a packet network, such as an IP network, forexample. Moreover, network 402 can connect the overlay network 400 withthe fabric 312 in FIG. 3. For example, VTEPs 408A-D can connect with theleaf switches 304 in the fabric 312 via network 402.

Hosts 406A-D include virtual tunnel end points (VTEP) 408A-D, which canbe virtual nodes or switches configured to encapsulate andde-encapsulate data traffic according to a specific overlay protocol ofthe network 400, for the various virtual network identifiers (VNIDs)410A-I. Moreover, hosts 406A-D can include servers containing a VTEPfunctionality, hypervisors, and physical switches, such as L3 switches,configured with a VTEP functionality. For example, hosts 406A and 406Bcan be physical switches configured to run VTEPs 408A-B. Here, hosts406A and 406B can be connected to servers 404A-D, which, in some cases,can include virtual workloads through VMs loaded on the servers, forexample.

In some embodiments, network 400 can be a VXLAN network, and VTEPs408A-D can be VXLAN tunnel end points (VTEP). However, as one ofordinary skill in the art will readily recognize, network 400 canrepresent any type of overlay or software-defined network, such asNVGRE, STT, or even overlay technologies yet to be invented.

The VNIDs can represent the segregated virtual networks in overlaynetwork 400. Each of the overlay tunnels (VTEPs 408A-D) can include oneor more VNIDs. For example, VTEP 408A can include VNIDs 1 and 2, VTEP408B can include VNIDs 1 and 2, VTEP 408C can include VNIDs 1 and 2, andVTEP 408D can include VNIDs 1-3. As one of ordinary skill in the artwill readily recognize, any particular VTEP can, in other embodiments,have numerous VNIDs, including more than the 3 VNIDs illustrated in FIG.4.

The traffic in overlay network 400 can be segregated logically accordingto specific VNIDs. This way, traffic intended for VNID 1 can be accessedby devices residing in VNID 1, while other devices residing in otherVNIDs (e.g., VNIDs 2 and 3) can be prevented from accessing suchtraffic. In other words, devices or endpoints connected to specificVNIDs can communicate with other devices or endpoints connected to thesame specific VNIDs, while traffic from separate VNIDs can be isolatedto prevent devices or endpoints in other specific VNIDs from accessingtraffic in different VNIDs.

Servers 404A-D and VMs 404E-I can connect to their respective VNID orvirtual segment, and communicate with other servers or VMs residing inthe same VNID or virtual segment. For example, server 404A cancommunicate with server 404C and VMs 404E and 404G because they allreside in the same VNID, viz., VNID 1. Similarly, server 404B cancommunicate with VMs 404F and 404H because they all reside in VNID 2.VMs 404E-I can host virtual workloads, which can include applicationworkloads, resources, and services, for example. However, in some cases,servers 404A-D can similarly host virtual workloads through VMs hostedon the servers 404A-D. Moreover, each of the servers 404A-D and VMs404E-I can represent a single server or VM, but can also representmultiple servers or VMs, such as a cluster of servers or VMs.

VTEPs 408A-D can encapsulate packets directed at the various VNIDs 1-3in the overlay network 400 according to the specific overlay protocolimplemented, such as VXLAN, so traffic can be properly transmitted tothe correct VNID and recipient(s). Moreover, when a switch, router, orother network device receives a packet to be transmitted to a recipientin the overlay network 400, it can analyze a routing table, such as alookup table, to determine where such packet needs to be transmitted sothe traffic reaches the appropriate recipient. For example, if VTEP 408Areceives a packet from endpoint 404B that is intended for endpoint 404H,VTEP 408A can analyze a routing table that maps the intended endpoint,endpoint 404H, to a specific switch that is configured to handlecommunications intended for endpoint 404H. VTEP 408A might not initiallyknow, when it receives the packet from endpoint 404B, that such packetshould be transmitted to VTEP 408D in order to reach endpoint 404H.Accordingly, by analyzing the routing table, VTEP 408A can lookupendpoint 404H, which is the intended recipient, and determine that thepacket should be transmitted to VTEP 408D, as specified in the routingtable based on endpoint-to-switch mappings or bindings, so the packetcan be transmitted to, and received by, endpoint 404H as expected.

However, continuing with the previous example, in many instances, VTEP408A may analyze the routing table and fail to find any bindings ormappings associated with the intended recipient, e.g., endpoint 404H.Here, the routing table may not yet have learned routing informationregarding endpoint 404H. In this scenario, the VTEP 408A may likelybroadcast or multicast the packet to ensure the proper switch associatedwith endpoint 404H can receive the packet and further route it toendpoint 404H.

In some cases, the routing table can be dynamically and continuouslymodified by removing unnecessary or stale entries and adding new ornecessary entries, in order to maintain the routing table up-to-date,accurate, and efficient, while reducing or limiting the size of thetable.

As one of ordinary skill in the art will readily recognize, the examplesand technologies provided above are simply for clarity and explanationpurposes, and can include many additional concepts and variations.

Depending on the desired implementation in the network 400, a variety ofnetworking and messaging protocols may be used, including but notlimited to TCP/IP, open systems interconnection (OSI), file transferprotocol (FTP), universal plug and play (UpnP), network file system(NFS), common internet file system (CIFS), AppleTalk etc. As would beappreciated by those skilled in the art, the network 400 illustrated inFIG. 4 is used for purposes of explanation, a network system may beimplemented with many variations, as appropriate, in the configurationof network platform in accordance with various embodiments of thepresent disclosure.

Having disclosed a brief introductory description of exemplary systemsand networks, the discussion now turns to FIGS. 5A and 5B, whichillustrate an example of infrastructure aware adaptive resourceallocation. As shown in FIG. 5A, system 500 includes resource manager502, infrastructure monitor 504 and computing nodes 506 (collectively).Computing nodes 506 can be any type of computing nodes included in adata center or hybrid cloud, such as servers, switches, routers, storage(e.g., all compute network or storage devices). Although only sevencomputing nodes 506 are shown, this is just an example, and not meant tobe limiting. System 500 can include any number of computing nodes 506.

Computing nodes 506 can be configured to host container instances. Forexample, computing nodes 506 can be configured to host containerinstances that provide micro-services of one or more applications.Resource manager 502 can be configured to manage allocation ofcontainers instances in system 500. For example, resource manager 502can be configured to allocate new container instances, remove containerinstances, relocate container instances, etc. Resource manager 502 cancommunicate with infrastructure monitor 504 to provide infrastructureaware adaptive resource allocation.

As shown, infrastructure monitor 504 can be configured to communicatewith computing nodes 506 to receive infrastructure data. Infrastructuremonitor 504 can be a computing device or application to which computingnodes 506 periodically communicate metrics and other infrastructuredata. For example, infrastructure monitor 504 can be implemented as partof a Software Defined Networking (SDN) application or as a part of anyresource manager framework itself using one or more availabletechnologies such as OpenFlow, SNMP, OnePK, ResetAPl, XMLApi, etc., tocommunicate and retrieve infrastructure data.

Infrastructure data can be data describing the individual computingnodes 506 as well as their underlying infrastructure. For example,infrastructure data can include CPU availability, memory usage, drivefailures (e.g., storage down), infrastructure related events (e.g.,power failures, network down, etc.), network latencies, RX/TX errors,bandwidth, QOS, packets dropped, power issues, quarantined portions ofthe network, network security issues, etc. Infrastructure monitor 504can continuously monitor and collect infrastructure data from thecomputing nodes and store the infrastructure data in tables.

Infrastructure monitor 504 can use the infrastructure data to determinehealth metrics for each of computing nodes 506. Health metrics can bedata that indicates or can be used to derive the health of computingnodes 506 to host a container instance. For example, health metrics canbe data that indicates whether a computing node 506 is experiencingperformance issues or, alternatively, performing at or near an optimallevel.

In some embodiments, the health metrics for a computing node 506 caninclude a health score calculated by infrastructure monitor 504. Ahealth score can be a score, such as a numerical value, that indicatesthe health of a computing node 506 to host a container instance. Forexample, a low health score may indicate that a computing node 506 isexperiencing performance issues, while a high health score can indicatethat a computing node 506 is performing at an optimal or near optimallevel.

Infrastructure monitor 504 can calculate a health score for a computingnode 506 in any way and based on any number of factors. In someembodiments, infrastructure monitor 504 can calculate individual scoresfor multiple factors and calculate the health score for a computing node506 based on the individual scores. An individual score can be a scoreassigned to a combination of one or more factors. For example, anindividual score can be assigned for an individual factor such asnetwork latency. The individual score for latency can indicate latencyexperienced by the computing node. For example, a low individual scorefor latency can indicate that the computing node is not experiencinglatency, whereas a high individual score for latency can indicate thatthe computing node is experiencing high latency. As another example, anindividual score can be assigned for a factor such as packets droppedand the score can indicate an number to indicate the severity of packetdrops detected.

In some embodiments, infrastructure monitor 504 can add the individualscores together to calculate the health score. As another example,infrastructure monitor 504 can determine the mean of the individualscores to calculate the health score for a computing node 506.

As another example, infrastructure monitor 504 can reduce and/orincrease a baseline score based on the infrastructure data to calculatethe health score. For example, infrastructure monitor 504 can begin witha baseline score of 100 and increase the score based on infrastructuredata indicating that a computing node 506 is not performing well, suchas detected errors, failures or increased latencies. Likewise,infrastructure monitor 504 can reduce the baseline score of 100 based oninfrastructure data indicating that a computing node 506 is performingwell. In some embodiments, infrastructure monitor 504 can apply weightswhen reducing and/or increasing the base line score. For example,infrastructure monitor 504 can reduce the baseline score by a weightedamount based on the type or severity of the detected problem.

In some embodiments, infrastructure monitor 504 can apply varyingweights to the individual scores when calculating the health score. Forexample, individual scores for factors considered to be of greaterimportance can be assigned a higher weight and therefore have greaterinfluence on the health score. Conversely, individual scores for factorsconsidered to be of lower importance can be assigned a lower weight andhave a lesser impact on the health score.

In addition to calculating health scores for computing nodes 506,infrastructure monitor 504 can also categorize the computing nodes basedon the health scores. The infrastructure monitor can categorize thecomputing nodes into one of a white list, grey list or black list, whichrepresent the relative health of computing nodes 506. Categorizing acomputing node 506 in the white list can indicate that the computingnode 506 is performing at an optimal or near optimal level (e.g., nothaving any major problems, latencies are within an expected range, noidentified security events, do not have any problems in the upstreameither with network or power or security). Being categorized in the greylist can indicate that a computing node 506 is not experiencing anymajor problems but there are some minor problems (e.g., slight increasein latencies, minor power or heating issues, new network security orresource events not yet classified as major problems, etc.). Beingcategorized in the black list can indicate that a computing node 506 hasmajor alerts or problems (e.g., major problems in the upstream, ToR orswitch with flapping ports, reduced bandwidth, events categorized asmajor issues, security alerts, etc.).

Resource manager 502 can be configured to work with infrastructuremonitor 504 to allocate container instances. For example, resourcemanager 502 can be configured to receive a request to allocate a newcontainer instance. In response, resource manager 502 can determine aset of candidate computing nodes 506 that are capable of hosting the newcontainer instance. For example, resource manager 502 can maintain dataidentifying computing nodes 506 and use an algorithm to select the setof candidate computing nodes 506.

Resource manager 502 can communicate with infrastructure monitor 504 torequest health metrics for the set of candidate computing nodes 506. Inresponse, infrastructure monitor 504 can search its database to gatherhealth metrics, including health scores and classifications, for therequested computing nodes 506 and provide the health metrics to resourcemanager 502. Resource manager 502 can then use the received healthmetrics to select an optimal computing node 506 from the set ofcandidate computing nodes 506 to host the new container instance. Forexample, resource manager 502 can determine a number of network issuesassociated with each candidate computing node, and select the candidatecomputing node with the least number of network issues as the optimalcomputing node. As another example resource manager 502 can select acandidate computing node that is categorized in the white list as theoptimal computing node. As another example, resource manager 502 canselect a candidate computing node with the highest health score as theoptimal computing node.

After selecting an optimal computing node, resource manager 502 cancommunicate with the optimal computing node to allocate the newcontainer instance in the optimal computing node. As shown in FIG. 5B,resource manager 502 can communicate with individual computing nodes 506to allocate container instances.

Resource manager 502 can also continually monitor computing nodes 506and proactively move container instances if needed. For example,resource manager 502 can periodically query infrastructure monitor 504for health metrics for computing nodes 506 and determine whether anycomputing nodes are experiencing performance issues. For example,resource manager can detect a failure, such as a server, switch or powerdistribution failure, which can create a hotspot in the existinginfrastructure. Resource manager 502 can relocate container instancesaway from and/or allocate new container instances around this hotspot.As another example, resource manger 502 can detect a power consumptionincrease in a specific location of the data center. Resource manager 502can proactively relocate container instances hosted on computing nodes506 in this affected area to computing nodes 506 in unaffected areas.

FIG. 6 illustrates an example method for infrastructure aware adaptiveresource allocation. It should be understood that there can beadditional, fewer, or alternative steps performed in similar oralternative orders, or in parallel, within the scope of the variousembodiments unless otherwise stated.

At step 602, a resource manager can receive a request to allocate afirst container instance in a network.

At step 604, the resource manager can determine a set of candidatecomputing nodes in the network that are capable of hosting the firstcontainer instance.

At step 606, the resource manager can request, from an infrastructuremonitor, health metrics for the set of candidate computing nodes. Theinfrastructure monitor can periodically receive infrastructure data fromthe network. Infrastructure data can include at least one of CentralProcession Unit (CPU) usage, disk usage, memory usage, computing nodestate, power consumption, temperature level, Tx and Rx counters, portqueue lengths, tail drops, network node state, routing table changes,intrusions or DDoS attacks. The health metrics can also include a healthscore for each candidate computing node as well as a classification ofeach candidate computing node as either in a white list, grey list orblack list.

At step 608, the resource manager can select, based on the healthmetrics for the set of candidate computing nodes, an optimal computingnode to host the first container instance. For example, the resourcemanager can determine a number of network issues for each candidatecomputing node and select the candidate computing node with the leastnumber of network issues as the optimal computing node. As anotherexample, the resource manager can select a candidate computing nodecategorized in the while list as the optimal computing node. As anotherexample, the resource manager can select a candidate computing node witha highest health score to be the optimal computing node.

At step 610, the resource manager can allocate the first containerinstance on the optimal computing node. After allocating the firstcontainer instance, the resource manager can periodically monitorperformance of the computing nodes. For example the resource manager canrequest, from the infrastructure monitor, health metrics for computingnodes in the network. The resource manager can determine, based on thehealth metrics, that a first computing node is experiencing a networkissue, and relocate at least one container instance hosted by the firstcomputing node to a second computing node in the network.

As one of ordinary skill in the art will readily recognize, the examplesand technologies provided above are simply for clarity and explanationpurposes, and can include many additional concepts and variations.

For clarity of explanation, in some instances the present technology maybe presented as including individual functional blocks includingfunctional blocks comprising devices, device components, steps orroutines in a method embodied in software, or combinations of hardwareand software.

In some embodiments the computer-readable storage devices, mediums, andmemories can include a cable or wireless signal containing a bit streamand the like. However, when mentioned, non-transitory computer-readablestorage media expressly exclude media such as energy, carrier signals,electromagnetic waves, and signals per se.

Methods according to the above-described examples can be implementedusing computer-executable instructions that are stored or otherwiseavailable from computer readable media. Such instructions can comprise,for example, instructions and data which cause or otherwise configure ageneral purpose computer, special purpose computer, or special purposeprocessing device to perform a certain function or group of functions.Portions of computer resources used can be accessible over a network.The computer executable instructions may be, for example, binaries,intermediate format instructions such as assembly language, firmware, orsource code. Examples of computer-readable media that may be used tostore instructions, information used, and/or information created duringmethods according to described examples include magnetic or opticaldisks, flash memory, USB devices provided with non-volatile memory,networked storage devices, and so on.

Devices implementing methods according to these disclosures can comprisehardware, firmware and/or software, and can take any of a variety ofform factors. Typical examples of such form factors include laptops,smart phones, small form factor personal computers, personal digitalassistants, rackmount devices, standalone devices, and so on.Functionality described herein also can be embodied in peripherals oradd-in cards. Such functionality can also be implemented on a circuitboard among different chips or different processes executing in a singledevice, by way of further example.

The instructions, media for conveying such instructions, computingresources for executing them, and other structures for supporting suchcomputing resources are means for providing the functions described inthese disclosures.

Although a variety of examples and other information was used to explainaspects within the scope of the appended claims, no limitation of theclaims should be implied based on particular features or arrangements insuch examples, as one of ordinary skill would be able to use theseexamples to derive a wide variety of implementations. Further andalthough some subject matter may have been described in languagespecific to examples of structural features and/or method steps, it isto be understood that the subject matter defined in the appended claimsis not necessarily limited to these described features or acts. Forexample, such functionality can be distributed differently or performedin components other than those identified herein. Rather, the describedfeatures and steps are disclosed as examples of components of systemsand methods within the scope of the appended claims. Moreover, claimlanguage reciting “at least one of” a set indicates that one member ofthe set or multiple members of the set satisfy the claim.

For clarity of explanation, in some instances the present technology maybe presented as including individual functional blocks includingfunctional blocks comprising devices, device components, steps orroutines in a method embodied in software, or combinations of hardwareand software.

Note that in certain example implementations, the optimization and/orplacement functions outlined herein may be implemented by logic encodedin one or more tangible, non-transitory media (e.g., embedded logicprovided in an application specific integrated circuit [ASIC], digitalsignal processor [DSP] instructions, software [potentially inclusive ofobject code and source code] to be executed by a processor, or othersimilar machine, etc.). The computer-readable storage devices, mediums,and memories can include a cable or wireless signal containing a bitstream and the like. However, when mentioned, non-transitorycomputer-readable storage media expressly exclude media such as energy,carrier signals, electromagnetic waves, and signals per se.

Methods according to the above-described examples can be implementedusing computer-executable instructions that are stored or otherwiseavailable from computer readable media. Such instructions can comprise,for example, instructions and data which cause or otherwise configure ageneral purpose computer, special purpose computer, or special purposeprocessing device to perform a certain function or group of functions.Portions of computer resources used can be accessible over a network.The computer executable instructions may be, for example, binaries,intermediate format instructions such as assembly language, firmware, orsource code. Examples of computer-readable media that may be used tostore instructions, information used, and/or information created duringmethods according to described examples include magnetic or opticaldisks, flash memory, USB devices provided with non-volatile memory,networked storage devices, and so on.

Devices implementing methods according to these disclosures can comprisehardware, firmware and/or software, and can take any of a variety ofform factors. Typical examples of such form factors include laptops,smart phones, small form factor personal computers, personal digitalassistants, and so on. Functionality described herein also can beembodied in peripherals or add-in cards. Such functionality can also beimplemented on a circuit board among different chips or differentprocesses executing in a single device, by way of further example.

The instructions, media for conveying such instructions, computingresources for executing them, and other structures for supporting suchcomputing resources are means for providing the functions described inthese disclosures.

Although a variety of examples and other information was used to explainaspects within the scope of the appended claims, no limitation of theclaims should be implied based on particular features or arrangements insuch examples, as one of ordinary skill would be able to use theseexamples to derive a wide variety of implementations. Further andalthough some subject matter may have been described in languagespecific to examples of structural features and/or method steps, it isto be understood that the subject matter defined in the appended claimsis not necessarily limited to these described features or acts. Forexample, such functionality can be distributed differently or performedin components other than those identified herein. Rather, the describedfeatures and steps are disclosed as examples of components of systemsand methods within the scope of the appended claims.

1. A method comprising: receiving, by a resource manager of a network, arequest to allocate a first container instance in the network;determining, by the resource manager, a set of candidate computing nodesin the network that are capable of hosting the first container instance;requesting, from an infrastructure monitor with infrastructure data fromthe network, health metrics for the set of candidate computing nodes;selecting, by the resource manager, based on the health metrics for theset of candidate computing nodes, an optimal computing node of the setof candidate computing nodes to host the first container instance.allocating the first container instance on the optimal computing node.2. The method of claim 1, wherein the infrastructure data includes atleast one of Central Procession Unit (CPU) usage, disk usage, memoryusage, computing node state, power consumption, temperature level, Txand Rx counters, port queue lengths, tail drops, network node state,routing table changes, intrusions, or DDoS attacks.
 3. The method ofclaim 1, wherein selecting the optimal computing node to host the firstcontainer instance comprises: for each candidate computing node from theset of candidate computing nodes, determining, based on the healthmetrics, a number of network issues associated with the candidatecomputing node; and selecting a candidate computing node with a leastnumber of network issues as the optimal computing node.
 4. The method ofclaim 1, wherein, each candidate computing node in the set of candidatecomputing nodes is classified in one of three classifications, the threeclassifications include a white list, a grey list, and a black list, thewhite list indicates one or more of the candidate computing node are notexperiencing a major problem, the grey list indicates one or more of thecandidate computing node are experiencing a minor problem, and the blacklist indicates one or more of the candidate computing node areexperiencing the major problem.
 5. The method of claim 1, whereinselecting the optimal computing node to host the first containerinstance comprises selecting a candidate computing node categorized in alist.
 6. The method of claim 1, wherein selecting the optimal computingnode to host the first container instance includes selecting a candidatecomputing node with a highest health score to be the optimal computingnode.
 7. The method of claim 1, further comprising: after allocating thefirst container instance, requesting, from the infrastructure monitor,health metrics for computing nodes in the network; determining, based onthe health metrics, that a first computing node is experiencing anetwork issue; and relocating at least one container instance hosted bythe first computing node to a second computing node in the network.
 8. Aresource manager comprising: one or more computer processors; and amemory storing instructions that, when executed by the one or morecomputer processors, cause the resource manager to: receive a request toallocate a first container instance in a network; determine a set ofcandidate computing nodes in the network that are capable of hosting thefirst container instance; request, from an infrastructure monitor withinfrastructure data from the network, health metrics for the set ofcandidate computing nodes; select, based on the health metrics for theset of candidate computing nodes, an optimal computing node of the setof candidate computing nodes to host the first container instance; andallocate the first container instance to the optimal computing node. 9.The resource manager of claim 8, wherein the infrastructure dataincludes at least one of Central Procession Unit (CPU) usage, diskusage, memory usage, computing node state, power consumption,temperature level, Tx and Rx counters, port queue lengths, tail drops,network node state, routing table changes, intrusions or DDoS attacks.10. The resource manager of claim 8, wherein selecting the optimalcomputing node to host the first container instance comprises: for eachcandidate computing node from the set of candidate computing nodes,determining a health score based on a number of network issuesassociated with the candidate computing node; and selecting a candidatecomputing node with a highest health score as the optimal computing nodeto host the first container instance.
 11. The resource manager of claim8, wherein, each candidate computing node in the set of candidatecomputing nodes is classified in one of three classifications, the threeclassifications include a white list, a grey list, and a black list, thewhite list indicates one or more of the candidate computing node are notexperiencing a major problem, the grey list indicates one or more of thecandidate computing node are experiencing a minor problem, and the blacklist indicates one or more of the candidate computing node areexperiencing the major problem.
 12. The resource manager of claim 8,wherein selecting the optimal computing node to host the first containerinstance includes selecting a candidate computing node categorized in alist.
 13. The resource manager of claim 8, wherein selecting the optimalcomputing node to host the first container instance includes selecting acandidate computing node with a highest health score to be the optimalcomputing node.
 14. The resource manager of claim 8, wherein theinstructions further cause the resource manager to: after allocating thefirst container instance, request, from the infrastructure monitor,health metrics for computing nodes in the network; determine, based onthe health metrics, that a first computing node is experiencing anetwork issue; and relocate at least one container instance hosted bythe first computing node to a second computing node in the network. 15.A non-transitory computer-readable medium storing instructions that,when executed by a resource manager, cause the resource manager to:receive a request to allocate a first container instance in a network;determine a set of candidate computing nodes in the network that arecapable of hosting the first container instance; request, from aninfrastructure monitor with infrastructure data from the network, healthmetrics for the set of candidate computing nodes; select, based on thehealth metrics for the set of candidate computing nodes, an optimalcomputing node of the set of candidate computing nodes to host the firstcontainer instance; and allocate the first container instance to theoptimal computing node.
 16. The non-transitory computer-readable mediumof claim 15, wherein the infrastructure data includes at least one ofCentral Procession Unit (CPU) usage, disk usage, memory usage, computingnode state, power consumption, temperature level, Tx and Rx counters,port queue lengths, tail drops, network node state, routing tablechanges, intrusions or DDoS attacks.
 17. The non-transitorycomputer-readable medium of claim 15, wherein selecting the optimalcomputing node to host the first container instance comprises: for eachcandidate computing node from the set of candidate computing nodes,determining, based on the health metrics, a number of network issuesassociated with the candidate computing node; and selecting a candidatecomputing node with a least number of network issues as the optimalcomputing node.
 18. The non-transitory computer-readable medium of claim15, wherein, each candidate computing node in the set of candidatecomputing nodes is classified in one of three classifications, the threeclassifications include a white list, a grey list, and a black list, thewhite list indicates one or more of the candidate computing node are notexperiencing a major problem, the grey list indicates one or more of thecandidate computing node are experiencing a minor problem, and the blacklist indicates one or more of the candidate computing node areexperiencing the major problem.
 19. The non-transitory computer-readablemedium of claim 15, wherein selecting the optimal computing node to hostthe first container instance includes selecting a candidate computingnode categorized in a list.
 20. The non-transitory computer-readablemedium of claim 15, wherein selecting the optimal computing node to hostthe first container instance includes selecting a candidate computingnode with a highest health score to be the optimal computing node.